|
|
|
|
|
|
|
Significant shifts in technology always seem to produce fear. When you stop to think about this, the fear usually derives from not knowing the technology from the ground up. Many books explain OOP, but there are new groups of professionals who are unaware of these. Also, many OOP novices are trying to learn it through Visual Basic. |
|
|
|
|
|
|
|
|
To understand how to use object-oriented programming, you must re-evaluate past programming habits. Nearly gone are the days when developers can try to successfully make ad hoc assumptions about business processes, intimate software design, and expected application behavior. |
|
|
|
|
|
|
|
|
Note
If you are experienced in OOP, you might still want to read this section for information to pass on to other programmers trying to migrate to OOP. |
|
|
|
|
|
|
|
|
|
Without the use of a proven object-oriented methodology, the complexities of a given project tend to lead to increased risk of failure or goals that are not fully achieved. In other words, it is more difficult to measure whether project goals have been achieved if critical assumptions about the application's architecture are made on-the-fly. Such ad hoc designs typically add more uncontrollable complexity to the application than originally expected. One fundamental idea behind object-oriented programming is to control the chaos normally associated with software development projects in order to promote reuse of objects. Reuse is achieved, in part, through well-designed classes. Well-designed classes are created by breaking down a complex problem into simpler abstractions. By iterating through one or more solutions to that problem, you can design classes with good attributes and methods, thus creating a strong class interface. You will learn about classes, their methods, and their attributes (including public class interfaces) in this book. |
|
|
|
|
|
|
|
|
On-the-fly programming (OTFP) is the easiest, most popular programming style that ever evolved in the software development community. For the most part, it has developed over the years as a response to growing expectations of computers by end users who want their software immediately. In OTFP, almost every function or sub is public and global. This idiom represents a higher level of abstraction absent in older programming practices. At least with Structured Analysis and Structured Design (SA/SD) methods, thought is given to creating well-defined functions and subroutines. Rapid Application Development (RAD) seeks to organize the industry's best practices into methods for rapidly providing turnkey solutions to end users. However, both SA/SD and RAD still do not fully address the need to break down problems documented in a requirements document into well-defined abstractions with grouped operations and attributes that can be |
|
|
|
|
|